Features Template

First Name  
Middle Name  
Last Name  
Company  
Email  
Feedback  

 

CAUTION: You must apply this template when you first create the topic. If you forget and then apply it later to an existing topic, the Java script code for highlighting search results will not be inserted into the topic true code. If the Java script code has been successfully added to the topic, you will see a red box at the end of the topic (see below).

Do not create sub-folders in the project without informing the Team Lead. As standard practice, we want to minimize the number of sub-folders.

NOTE: If you notice any topic files in this project that do not have the red box at the end, please notify your Team Lead.

IMPORTANT: Use the following headings to format all Features topics. Replace the text between the angle brackets with your topic content. Delete all non-heading text above, and including, this line before closing the topic.

IMPORTANT: If the headings below contain more than one page of information, create a topic for each heading. Use an Overview heading to start the Description topic.
If the headings below will contain more than one topic, create TOC sub-books for each heading.

Description:

<Text description of the feature from one sentence to multiple paragraphs. Major features may require more than one topic for a description. If this is the case, group these topics in a book titled "Description" under the book titled "<featureName>.

Conditions and Feature Interactions

Programming

<Type None if there are no programming procedures required.>

OR

OR

<List multiple programming options with a stem sentence ("To program the ABC feature:")>

<For example:

To program a PRI trunk for AOC (Universal NSU)

NOTE: When referencing a form include the following graphic:

    

The graphic is a link to the ESM form in the MiVB Sys Admin Tool. Clicking it opens the form. The properties of the image (double-click to see them) must include the form name exactly as it appears in the Sys Admin Tool. The name goes in the ALT text field:

The icon goes at the end of the sentence if that's where the form reference is located. If the reference is closer to the start of the sentence put the icon adjacent to the reference and enclose it in parenthesis. Examples:

To program Automatic Route Selection:

  1. Trunk Groups form

Create a trunk group number and assign trunks to the trunk group.

  1. Call Progress Tone Detection form (optional)

Create an ARS Call Progress Tone Detection plan.

  1. ARS Digit Modification Plans form

For each Digit Modification Number, specify the number of dialed digits to absorb and the digits to be inserted.

Policies are assigned to users (one per user only) in the User Authorization Profiles form ( ) and distributed to all cluster elements by SDS.

NOTE: The heading 2 element (h2) as seen in HTML view requires an ID. This ID takes the form "Programming <feature name" and is used when the task is loaded into the Task List in ESM.

Device Support

<Snippet. Use for phone features only. Omit section if not applicable.>

Operation

<Optional. Use for phone features only. Omit section if not applicable>

<Text description for simple operation.  

OR

Stem sentence ("To program the ABC feature:") with numbered instructions for more complex operation. This section may have multiple operation modes (use stem sentence + instructions for each mode) or multiple phone instances (list the stem sentence + instructions under the bold phone name/number).>

Example

<(Optional - omit section if not applicable.) Link to an example of programming this feature in a real-world setting. Example requirement determined by Product Support.>

Related Topics